-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Introduce Common Open Source Tooling into Codebase to Increase Productivity and Developer Experience #43
Conversation
❌ Deploy Preview for cuhacking-portal-test-deployment failed. Why did it fail? →
|
04c5cf7
to
046bc71
Compare
7cfa809
to
354039e
Compare
354039e
to
f7a4330
Compare
Looks like Will investigate more. |
Since it is relevant, |
After some more testing it looks like it was not fixed. |
fixplsworkplsworkabcd
🤣lazygit-hunks-and-commitizen-demo.mp4
Our platform is now versioned according to the SemVer specification with Semantic Release
What's better than one pipeline using
pnpm
you ask? Well of course it's three pipelines usingbun
🤯Triple the vroom vroom 🤖
TODO: Set up caching and run pipelines in aforementioned order rather than in parallel, but keep them on separate files. We can then say
it failed the build/test/release pipeline
. Makes communication and debugging a bit easier.